Adjusted documentation about packages to v1/v2 instead of old/new #3237
Conversation
We felt in discussion internally that v1/v2 was easier to understand especially if we also include how they are implemented: v1 packages promise (package_method) v2 packages promise (package_module) This leaves easier room for a v3 if that ever needs to happen. v1(old) packages promise still has several advantages: - support for more different package managers such as pip, brew, etc. - support for bulk operations by default Ticket: CFE-4315 Changelog: title
|
@cf-bottom jenkins please |
|
this is related to cfengine/core#5434 (CFE-4315) but isn't dependent on it from a code point of view so am not putting "together" so I can get a fast docs build. |
|
Sure, I triggered a build: Jenkins: https://ci.cfengine.com/job/fast-build-and-deploy-docs-master/537/ Documentation: http://buildcache.cfengine.com/packages/build-documentation-pr/jenkins-fast-build-and-deploy-docs-master-537/output/_site/ |
|
@cf-bottom jenkins another go please |
|
Sure, I triggered a build: Jenkins: https://ci.cfengine.com/job/fast-build-and-deploy-docs-master/538/ Documentation: http://buildcache.cfengine.com/packages/build-documentation-pr/jenkins-fast-build-and-deploy-docs-master-538/output/_site/ |
|
@cf-bottom jenkins |
|
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/fast-build-and-deploy-docs-master/539/ Documentation: http://buildcache.cfengine.com/packages/build-documentation-pr/jenkins-fast-build-and-deploy-docs-master-539/output/_site/ |
|
@cf-bottom jenkins |
|
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/fast-build-and-deploy-docs-master/540/ Documentation: http://buildcache.cfengine.com/packages/build-documentation-pr/jenkins-fast-build-and-deploy-docs-master-540/output/_site/ |
|
|
|
|
|
|
We felt in discussion internally that v1/v2 was easier to understand especially if we also include how they are implemented:
v1 packages promise (package_method)
v2 packages promise (package_module)
This leaves easier room for a v3 if that ever needs to happen.
v1(old) packages promise still has several advantages:
Ticket: CFE-4315
Changelog: title